Ensuring automatic season change demand resets in a mesh type network of telemetry devices

ABSTRACT

Methods and systems of enforcing a season change demand reset in a meter that communicates via a wireless network. When billing data is received by a server, it is accompanied by a season change demand reset counter. The counter is compared to a counter stored on the server. If the received counter is different that an expected value based on the server counter, it is determined that the meter missed a season change demand reset. The server then instructs the meter to perform a billing read and to perform a season change demand reset to ensure that accurate demand data is received by the server.

FIELD OF THE INVENTION

The present invention relates to wireless networks for collecting data, and more particularly, to systems and methods for enforcing a season change in a telemetry device, such as an electronic meter.

BACKGROUND OF THE INVENTION

The collection of meter data from electrical energy, water, and gas meters has traditionally been performed by human meter-readers. The meter-reader travels to the meter location, which is frequently on the customer's premises, visually inspects the meter, and records the reading. The meter-reader may be prevented from gaining access to the meter as a result of inclement weather or, where the meter is located within the customer's premises, due to an absentee customer. This methodology of meter data collection is labor intensive, prone to human error, and often results in stale and inflexible metering data.

Some meters have been enhanced to include a one-way radio transmitter for transmitting metering data to a receiving device. A person collecting meter data that is equipped with an appropriate radio receiver need only come into proximity with a meter to read the meter data and need not visually inspect the meter. Thus, a meter-reader may walk or drive by a meter location to take a meter reading. While this represents an improvement over visiting and visually inspecting each meter, it still requires human involvement in the process.

An automated means for collecting meter data involves a fixed wireless network. Devices such as, for example, repeaters and gateways are permanently affixed on rooftops and pole-tops and strategically positioned to receive data from enhanced meters fitted with radio-transmitters. Typically, these transmitters operate in the 902-928 MHz range and employ Frequency Hopping Spread Spectrum (FHSS) technology to spread the transmitted energy over a large portion of the available bandwidth.

Data is transmitted from the meters to the repeaters and gateways and ultimately communicated to a central location. While fixed wireless networks greatly reduce human involvement in the process of meter reading, such systems require the installation and maintenance of a fixed network of repeaters, gateways, and servers. Identifying an acceptable location for a repeater or server and physically placing the device in the desired location on top of a building or utility pole is a tedious and labor-intensive operation. Furthermore, each meter that is installed in the network needs to be manually configured to communicate with a particular portion of the established network. When a portion of the network fails to operate as intended, human intervention is typically required to test the effected components and reconfigure the network to return it to operation.

In wireless networks for reading telemetry devices, it is possible that one or more devices may migrate from one communication path to another to communicate to the central location. It is possible that after a migration, that a device will failed to be instructed and/or read billing information in a timely fashion. If a season change has occurred between missed billing reads, it is possible that billing data may be processed incorrectly.

Thus, while existing fixed wireless systems have reduced the need for human involvement in the daily collection of meter data, such systems require substantial human investment in planning, installation, and maintenance. In addition, there is a need for a system to manage the collection of usage and other data from the meter for billing and other applications.

SUMMARY OF THE INVENTION

Methods and systems of enforcing a season change demand reset in a meter that communicates via a wireless network. When billing data is received by a server, it is accompanied by a season change demand reset counter. The counter is compared to a counter stored on the server. If the received counter is different than an expected value based on the server counter, it is determined that the meter missed a season change demand reset. The server then instructs the meter to perform a billing read and to perform a season change demand reset to ensure that accurate demand data is received by the server.

It may be determined by the system if the meter migrated from one collector to another before being instructed to take a season change snapshot and reset its season change demand register.

Additional features and advantages of the invention will be made apparent from the following detailed description of illustrative embodiments that proceeds with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing summary, as well as the following detailed description of preferred embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the drawings exemplary constructions of the invention; however, the invention is not limited to the specific methods and instrumentalities disclosed. In the drawings:

FIG. 1 is a diagram of a wireless system for collecting data from remote devices;

FIG. 2 expands upon the diagram of FIG. 1 and illustrates a system in which the present invention is embodied; and

FIG. 3 illustrates a meter migrating from one collector to another.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Exemplary systems and methods for gathering meter data are described below with reference to FIGS. 1-3. It will be appreciated by those of ordinary skill in the art that the description given herein with respect to those figures is for exemplary purposes only and is not intended in any way to limit the scope of potential embodiments.

Generally, a plurality of meter devices, which operate to track usage of a service or commodity such as, for example, electricity, water, and gas, are operable to wirelessly communicate with each other. A collector is operable to automatically identify and register meters for communication with the collector. When a meter is installed, the meter becomes registered with the collector that can provide a communication path to the meter. The collectors receive and compile metering data from a plurality of meter devices via wireless communications. A communications server communicates with the collectors to retrieve the compiled meter data.

FIG. 1 provides a diagram of an exemplary metering system 110. System 110 comprises a plurality of meters 114, which are operable to sense and record usage of a service or commodity such as, for example, electricity, water, or gas. Meters 114 may be located at customer premises such as, for example, a home or place of business. Meters 114 comprise an antenna and are operable to transmit data, including service usage data, wirelessly. Meters 114 may be further operable to receive data wirelessly as well. In an illustrative embodiment, meters 114 may be, for example, a electrical meters manufactured by Elster Electricity, LLC.

System 110 further comprises collectors 116. Collectors 116 are also meters operable to detect and record usage of a service or commodity such as, for example, electricity, water, or gas. Collectors 116 comprise an antenna and are operable to send and receive data wirelessly. In particular, collectors 116 are operable to send data to and receive data from meters 114. In an illustrative embodiment, meters 114 may be, for example, an electrical meter manufactured by Elster Electricity, LLC.

A collector 116 and the meters 114 for which it is configured to receive meter data define a subnet/LAN 120 of system 110. As used herein, meters 114 and collectors 116 may be considered as nodes in the subnet 120. For each subnet/LAN 120, data is collected at collector 116 and periodically transmitted to a data collection server 206. The data collection server 206 stores the data for analysis and preparation of bills. The data collection server 206 may be a specially programmed general purpose computing system and may communicate with collectors 116 wirelessly or via a wire line connection such as, for example, a dial-up telephone connection or fixed wire network.

Generally, collector 116 and meters 114 communicate with and amongst one another using any one of several robust wireless techniques such as, for example, frequency hopping spread spectrum (FHSS) and direct sequence spread spectrum (DSSS). As illustrated, meters 114 a are “first level” meters that communicate with collector 116, whereas meters 114 b are higher level meters that communicate with other meters in the network that forward information to the collector 116.

Referring now to FIG. 2, there is illustrated a system 200 in which the present invention may be embodied. The system 200 includes a network management server 202, a network management system (NMS) 204 and a data collection server 206 that together manage one or more subnets/LANs 120 and their constituent nodes. The NMS 204 tracks changes in network state, such as new nodes registering/unregistering with the system 200, node communication paths changing, etc. This information is collected for each subnet/LAN 120 and are detected and forwarded to the network management server 202 and data collection server 206.

In accordance with an aspect of the invention, communication between nodes and the system 200 is accomplished using the LAN ID, however it is preferable for customers to query and communicate with nodes using their own identifier. To this end, a marriage file 208 may be used to correlate a customer serial number, a manufacturer serial number and LAN ID for each node (e.g., meters 114 a and collectors 116) in the subnet/LAN 120. A device configuration database 210 stores configuration information regarding the nodes. For example, in the metering system 110, the device configuration database may include data regarding time of use (TOU) switchpoints, etc. for the meters 114 a and collectors 116 communicating to the system 200. A data collection requirements database 212 contains information regarding the data to be collected on a per node basis. For example, a user may specify that metering data such as load profile, demand, TOU, etc. is to be collected from particular meter(s) 114 a. Reports 214 containing information on the network configuration may be automatically generated or in accordance with a user request.

The network management system (NMS) 204 maintains a database describing the current state of the global fixed network system (current network state 220) and a database describing the historical state of the system (historical network state 222). The current network state 220 contains data regarding current meter to collector assignments, etc. for each subnet/LAN 120. The historical network state 222 is a database from which the state of the network at a particular point in the past can be reconstructed. The NMS 204 is responsible for, amongst other things, providing reports 214 about the state of the network. The NMS 204 may be accessed via an API 220 that is exposed to a user interface 216 and a Customer Information System (CIS) 218. Other external interfaces may be implemented in accordance with the present invention. In addition, the data collection requirements stored in the database 212 may be set via the user interface 216 or CIS 218.

The data collection server 206 collects data from the nodes (e.g., collectors 116) and stores the data in a database 224. The data includes metering information, such as energy consumption and may be used for billing purposes, etc. by a utility provider.

The network management server 202, network management system 204 and data collection server 206 communicate with the nodes in each subnet/LAN 120 via a communication system 226. The communication system 226 may be a Frequency Hopping Spread Spectrum radio network, a mesh network, a Wi-Fi (IEEE 802.11) network, a Wi-Max (IEEE 802.16) network, a land line (POTS) network, etc., or any combination of the above and enables the system 200 to communicate with the metering system 110.

Demand meters within the metering system 110 are typically put onto a billing schedule by the collector 116 and the system 200. The billing schedule may be set in accordance with a billing ID for a particular meter. The demand meters are read according to the schedule to determine a quantity of power consumed at a customer location. Reading of demand meters by the system 200 is often accomplished one of two ways: (1) contact the meter, read the demand data and reset the meter in a communication session, or (2) configure the meter self-read and reset, and read the demand data at a time after the reset (i.e., the meter operates as a so-called “auto-read” meter). A demand reset begins a new demand billing period.

In a system such as that shown in FIGS. 1 and 2, the system 200 is aware of season change dates for Time of Use (TOU) schedules, meter assignments to the TOU schedules, and the current state and previous state of the network (e.g., such as end meter/device-collector assignments). A scheduling entity within the network 200 tracks the need to perform certain activities after the season change date has passed. After a season change midnight crossing, but before the billing read for a meter, the scheduling entity queries the system for any devices that are on TOU schedules that went through a season change. For any such end devices, the system retrieves snapshots of season change data and a current reset count by querying the collector for that end device, as well as incrementing the system reset counters to reflect that the meter/end device has undergone a season change.

Alternatively, a telemetry device that is capable of initiating an inbound communication to the system 200 (e.g., telephone, wireless, packet network, etc.) may report a snapshot of season change data and a current reset count. Thus, if a collector for a device is capable of initiating an inbound communication, it may report season change data for all its registered nodes.

The system 200 tracks all of the telemetry devices that recorded a successful season change by comparing reset counts, updating the devices that have reset and incremented their counts and recorded the date and time of the update. Additionally, the system also records the devices that have not indicated the occurrence of a successful season change reset and uses its knowledge of current and previous state of the network to verify successful processing of season changes by a node/meter.

For example, with reference to FIG. 3, if the node/meter 114 a moves from collector A to collector B after a season change, but before the system begins querying for season change snapshots, the system 200 queries the previous collector (collector A) for meter 114 a using the previous network state 222 to confirm that a season change demand reset occurred and that a season change snapshot was recorded (or alternatively, as noted above, the system 200 is notified of the same via an inbound communication from collector A).

However, the collector A may not instruct (“arm”) the meter 114 a to perform a season change until 24-hours before the time when the change is to occur. This method of performing a season change advantageously eliminates the need for accurate time-keeping and calendaring in the meter, thus allowing the meter to be low cost. A problem occurs when the node 114 a misses a season change when it loses communication with its collector prior to being “armed” for the season change and then has communications restored to the same collector or another after the season change midnight.

In FIG. 3, the system 200 detects the restoration of communications by receiving a communication from collector B that node 114 a has registered with it, or during its next communication with collector B, when collector B would inform the system 200 of the registration of node 114 a. If the meter 114 a was not armed, the demand reset counter reported for the meter 114 a will be the same as the count maintained by the system 200. In other words, if the meter was armed and the reset occurred at the season change midnight, the meter would report a demand reset count that is one more than the count maintained by the system 200.

When this condition exists, the meter 114 a is tagged as having missed the season change. The meter's new collector (collector B) is instructed to synchronously reset the meter's season change demand registers and read the billing data from the meter 114 a. This may be accomplished by using a system for managing spontaneously migrating nodes such as disclosed in U.S. patent application Ser. No. 10/949,682, filed Sep. 24, 2004, entitled “System for Automated Management of Spontaneous Node Migration in a Distributed Fixed Wireless Network,” which is incorporated herein by reference in its entirety. If the operation fails, the system 200 will again contact the collector B to retry the operation until the meter data is successfully read.

While systems and methods have been described and illustrated with reference to specific embodiments, those skilled in the art will recognize that modification and variations may be made without departing from the principles described above and set forth in the following claims. Accordingly, reference should be made to the following claims as describing the scope of disclosed embodiments. 

1. A system for enforcing a season change in a meter operating within a wireless metering network, comprising: a network configuration server that maintains a network state; and a data collection server that receives a counter from said meter, wherein when said data collection server receives said counter and performs a comparison of said counter to an expected value, and wherein said network configuration server requests said meter to download a season change snapshot and perform a season change demand reset as a result of said comparison.
 2. The system of claim 1, further comprising a first collector associated with a first communication path from said meter to said system, and wherein said network configuration server instructs said first collector to contact said meter, download said season change snapshot and perform said season change demand reset.
 3. The system of claim 2, further comprising a second collector associated with a second communication path from said meter to said system, wherein it is determined said meter has migrated from said second communication path to said first communication path prior to instructing said first collector to contact said meter.
 4. The system of claim 1, wherein said meter is configured as an auto-read meter and is instructed to perform said season change demand reset at a time in advance of reading said season change snapshot.
 5. The system of claim 1, wherein said meter and said system increment said counter and said expected value for each season change demand reset by said meter.
 6. A method for enforcing a season change demand reset in a meter operating within a wireless metering network, comprising: receiving a counter from a meter at a data collection server; comparing said counter to a second counter; and requesting said meter to download a season change snapshot and perform a season change demand reset as a result of said comparing.
 7. The method of claim 6, further comprising: communicating said season change snapshot to a first collector associated with a first communication path; and instructing said first collector to contact said meter to perform a billing read and said season change demand reset.
 8. The system of claim 7, further comprising: determining that said meter has migrated from a second communication path having a second collector; and instructing said first collector to contact said meter after determining said meter has migrated from said second path.
 9. The method of claim 6, further comprising: configuring said meter as an auto-read meter; and instructing said meter to perform said season change demand reset at a time in advance of reading said season change snapshot.
 10. The method of claim 9, said instructing said meter in accordance with a Time of Use (TOU) schedule.
 11. The method of claim 6, further comprising incrementing said counter and said second counter for each season change demand reset performed by said meter.
 12. A computer-readable medium having computer-executable instructions for instructing a computing device to perform the steps of enforcing a season change demand reset in a meter operating within a wireless metering network, said steps comprising: receiving a counter from a meter at a data collection server; comparing said counter to a second counter; and requesting said meter to download a season change snapshot and perform a season change demand reset as a result of said comparing.
 13. The computer-readable medium of claim 12, further comprising instructions for performing the steps of: communicating said season change snapshot to a first collector associated with a first communication path; and instructing said first collector to contact said meter to perform a billing read and said season change demand reset.
 14. The computer-readable medium of claim 13, further comprising instructions for performing the steps of: determining that said meter has migrated from a second communication path having a second collector; and instructing said first collector to contact said meter after determining said meter has migrated from said second path.
 15. The computer-readable medium of claim 12, further comprising instructions for performing the steps of: configuring said meter as an auto-read meter; and instructing said meter to perform said season change demand reset at a time in advance of reading said season change snapshot.
 16. The computer-readable medium of claim 15, said instructing said meter in accordance with a Time of Use (TOU) schedule.
 17. The computer-readable medium of claim 12, further comprising instructions for performing the step of incrementing said counter and said second counter for each season change demand reset by said meter. 